Lost in wiki space? Blank-Wikipage-Syndrome? Where to add? How to find? No fun anymore?
projectdoc - as an add-on for Confluence - supports teams to communicate. Effective communication is essential for successful team work. Stakeholders communicate with each other and their future selves.
projectdoc focuses on indirect communication that is based on documents and records. We call the whole collection of these artifacts documentation.
projectdoc claims to support teams to create documentation that is
- easier to write
- easier to extend
- easier to reuse
- easier to navigate
- easier to search
- easier to read
Communication
Communication may be direct or indirect. Direct communication (collaborating on a user story map or talking to a customer) is usually preferred, because of its interaction options and its additional non-verbal channels.
Indirect communication (software architecture document or error codes report in a user manual) also has their benefits:
- it easily scales
- it works well with distributed teams
- it makes knowledge available on the long run
- it allows to be digested at the reader's pace
Certainly this is a big claim. Can we proof it?
Let's take a tour to the basics of projectdoc and explain why projectdoc makes using a wiki as a tool for team communication and collaboration much easier.
Here is the outline of this article: